Skip to content

Conversation

@interzoid
Copy link

What

This PR adds a new connector for source Standardize Company Names API (source-standardize-company-names-api).

Contributor-provided connector description:

This API standardizes/normalizes organization and company names into their official name standard using an advanced 'closest match' AI algorithm. It handles various input variations including abbreviations, alternate spellings, and multiple languages, converting them all to standardized English equivalents. Perfect for data cleansing, analytics/reporting, and maintaining consistent organization records across your data assets and systems.

The contributor provided the following description of the change:

Initial

Details

Expand for list of spec properties and streams

Configuration

Input Type Description Default Value
api_key string API Key.

Streams

Stream Name Primary Key Pagination Supports Full Sync Supports Incremental
standard No pagination

Reviewer checklist

  • Consider how the connector handles pagination (docs).
  • Help the contributor upload an icon that follows our icon design guidelines
  • Click into the CI workflows that wait for a maintainer to run them, which should trigger CI runs

@CLAassistant
Copy link

CLAassistant commented Nov 18, 2025

CLA assistant check
All committers have signed the CLA.

@github-actions
Copy link
Contributor

👋 Welcome to Airbyte!

Thank you for your contribution from interzoid/airbyte! We're excited to have you in the Airbyte community.

Helpful Resources

PR Slash Commands

As needed or by request, Airbyte Maintainers can execute the following slash commands on your PR:

  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions.
  • /run-connector-tests - Runs connector tests.
  • /run-cat-tests - Runs CAT tests.
  • /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).

If you have any questions, feel free to ask in the PR comments or join our Slack community.

Tips for Working with CI

  1. Pre-Release Checks. Please pay attention to these, as they contain standard checks on the metadata.yaml file, docs requirements, etc. If you need help resolving a pre-release check, please ask a maintainer.
    • Note: If you are creating a new connector, please be sure to replace the default logo.svg file with a suitable icon.
  2. Connector CI Tests. Some failures here may be expected if your tests require credentials. Please review these results to ensure (1) unit tests are passing, if applicable, and (2) integration tests pass to the degree possible and expected.
  3. (Optional.) BYO Connector Credentials for tests in your fork. You can optionally set up your fork with BYO credentials for your connector. This can significantly speed up your review, ensuring your changes are fully tested before the maintainers begin their review.

📝 Edit this welcome message.

@DanyloGL
Copy link
Collaborator

DanyloGL commented Nov 24, 2025

/run-connector-tests

Connector CI Tests Started

These tests will leverage Airbyte's integration test credentials.

Check job output.
✅ Connector CI Tests job completed successfully. See logs for details.

@DanyloGL
Copy link
Collaborator

@DanyloGL DanyloGL moved this from New PRs to Waiting Contributor in 🧑‍🏭 Community Pull Requests Nov 24, 2025
@interzoid
Copy link
Author

Danylo,

Yes it's reasonable and makes perfect sense if it's possible to add multiple APIs as separate streams within one connector, especially as we have even more streams/APIs that I would like to add over time. I will try to do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Waiting Contributor

Development

Successfully merging this pull request may close these issues.

4 participants